During the process of looking for the QueueControl leak today, the profiler was indirectly showing lots references on RemotingConnectionImpl, going through two static fields, that are using some sort of thread pool: - InVMConnection::factory - ConnectionManagerImpl::pingExecutor The references were aways inside some method on a thread. Probably those references would be gone as soon as the pool is used, but it would be much easier to cleanup leaks if we aways recreate those pools on tearDowns(). (a simple kill -3 would show a cleaned memory if setting the dump-memory option on the VM) I was thinking about creating a method named recreatePingExecutor on ConnectionManagerImpl and another named recreateFactory on InVMConnection, and those methods would be marked to be used by tests only. Is there a problem on that approach? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225416#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...