We suspect that our stateless EJBs are leaking.
Attaching jmx-console stats and path to GC for one of the leaking beans from a test system that has been running on small load for 12 hours.
If I annotate a leaking bean to use another pooling class (as suggested by http://community.jboss.org/thread/110175) the leak seems to go away.
So my guess is that the default ThreadLocalPool retains the EJB instances and the mechanism for removing old ones is somehow misconfigured?
Should I make all our beans to use StrictMaxPool instead?
Retrieving data ...