Jboss Version: 4.2.3GA JBoss WS version: 3.0.5 GA We are running a portal application (using JBoss portal) in a production environment; The portal interacts with a service tier comprised of EJB's (there are few web services implemented using stateless EJB's) We are observing that the old gen becomes full after few hours. Took a heap dump and analyzed using Eclipse MAT. It reports the following as leak suspects: Problem Suspect 1 anonymous wrote : One instance of "org.jboss.ejb3.stateless.StatelessContainer" loaded by "org.jboss.mx.loading.UnifiedClassLoader3 @ 0x8c437030" occupies 45,654,248 (11.77%) bytes. The memory is accumulated in one instance of "java.util.LinkedList$Entry" loaded by "<system class loader>". Problem Suspect 2 anonymous wrote : 277 instances of "org.jboss.ejb3.stateless.StatelessBeanContext", loaded by "org.jboss.mx.loading.UnifiedClassLoader3 @ 0x8c437030" occupy 186,304,176 (48.05%) bytes. These instances are referenced from one instance of "java.util.HashMap$Entry[]", loaded by "<system class loader>" Hint anonymous wrote : The problem suspects 1 and 2 may be related, because the reference chains to them have a common beginning. | org.jboss.remoting.transport.socket.SocketServerInvoker$ServerSocketRefresh @ 0x8c41b908 ServerSocketRefresh Thread | Can someone suggest how to proceed ahead with this? Thanks Venu View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252207#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...