So the TomcatDeployer is a similar problem, but this time it is JBossXB's usage of BeanInfo.newInstance() which also dispatches a construct joinpoint. That's one is harder to fix since jboss-reflect can't depend on jboss-mdr (the dependency is the reverse) to mask the metadata stack. Maybe we need to think about doing this in a different way so it is less hacky to differentiate constructions that need to pass a MetaData object (and should explicitly do so) versus the ad hoc usage of BeanInfo/ConstructorJoinPoints which don't and shouldn't therefore be creating AOP proxies. I've started a thread on this in the MC forum http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166401#... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166402#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...