Perhaps it was an EJB3 container bug - in which case I'm sure the fix will be in JBoss 4.2. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4023365#4023365 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4023365