That's expected yes. The clusteredentity tests are unrelated to this work; I'll look this week. IIRC, that has to do w/ including "ear=foo.jar" in ObjectNames even when no ear is involved; it's a matter of making the test expect that behavior (or better yet, getting rid of that behavior if the metadata now allows us to detect it). 18 clusteredsession failures sounds right. If you hack in a workaround to EJBTHREE-1471 [1], that should drop to 2. The two represents a known and acceptable change in behavior from AS 4.x where I haven't had time to tweak the test to account for it. [1] The workaround; this doesn't remove CL leak; just blunt-force stops it from affecting later deployments, allowing testsuite to run properly: | Index: /home/bes/dev/ejb3/trunk/proxy/src/main/java/org/jboss/ejb3/proxy/factory/session/SessionProxyFactoryBase.java | =================================================================== | --- /home/bes/dev/ejb3/trunk/proxy/src/main/java/org/jboss/ejb3/proxy/factory/session/SessionProxyFactoryBase.java (revision 77377) | +++ /home/bes/dev/ejb3/trunk/proxy/src/main/java/org/jboss/ejb3/proxy/factory/session/SessionProxyFactoryBase.java (working copy) | @@ -212,7 +212,11 @@ | constructor = this.createProxyConstructor(businessInterfaces, tcl); | | } | - catch (ClassNotFoundException cce) | +// catch (ClassNotFoundException cce) | +// { | +// // Ignore | +// } | + catch (Throwable t) // BES: temporary workaround to CL leak issue so I can test | { | // Ignore | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172322#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...