"bstansberry" wrote : I think catching the error is good. How about also trying to limit this code path? Okay, good. Turns out EJBTHREE-1442 was the source of most (if not all) of the CL Leaks. There's still one test failure remaining, "testSimpleEjb", where it looks like a Proxy is a reference held by an InvocationResponse, which is held from a remoting ServerThread...not sure what I can do about this one just yet. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172844#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...