It is actually a (fixed) bug in JBoss EJB3. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033258#4033258 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033258