It's actually on EAP 5.0.0, and I was going to try EAP 5.0.1. I would assume the fixes for this problem made it into EAP 5.0.0?
Reply to this message by going to Community
Start a new discussion in EJB 3.0 at Community