by default, connection-leak-timeout is not enabled.
Since bean container controls the life (destroy), it is difficult to arrive at a leak timeout value. Making sure that the ejb-container's "idle-timeout-in-seconds" is less than half of connection pool's connection-leak-timeout value will help to minimize this log.
Actual suggestion would be to use the connection (lookup) as and when required and close when it is not needed any more. Since these connections are pooled, there won't be any performance impact.
[Message sent by forum member 'jr158900' (jr158900)]
http://forums.java.net/jive/thread.jspa?messageID=276224