Do you know whether this bug will be solved in 4.0.5 + EJB3 RCx ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971031#3971031 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971031