You would be better to direct this question to the EJB3 forum, and it would be even better
if you could produce a test case that shows this happening w/o Seam, and just EJB3 beans,
since I doubt it has anything to do with Seam.
Does the problem still occur if you use a Seam-managed persistence context?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989972#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...