MBeanProxyExt.create is creating a new ClassLoader and forcing a loadClass to return an instance of a proxy using that classLoader. I guess this is done to make sure a redeployment leakage is not going to happen. IMO it would be better just use the original ClassLoader, and make sure applications are releasing instances to the proxy. Creating a new ClassLoader here would just mascarade a real problem, and besides create a worse leakage. On the case of JBAS-3428 I guess we should just revert to MBeanProxy.get. (I would like to hear from others), and if we see a redeployment leakage we should clear references to its proxies. I also thinkg MBeanProxyExt.create should behave the same way as MBeanProxy.get. Just IMHO. Clebert Suconic View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960837#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...