This is a heads up on the WS and EJB3 issue which Alessio found in the testsuite against JBPAPP_5_1 branch. Carlo explained this issue to me on Friday and I was able to fix the issue in EJB3 through https://jira.jboss.org/browse/EJBTHREE-2098. The changes required in EJB3 has been committed. A ejb3-deployers(1.1.4) and a ejb3-bom-eap5 (0.1.2) is required from EJB3 to bring in the fix. I can release the ejb3-deployers, but for ejb3-bom-eap5, I would need Carlo's help.
Note that, while testing this fix, I noticed that this exposes a different issue which was discussed here http://community.jboss.org/thread/149776. The fix for this WS issue will require a release of JBoss WS project. I had a chat with Alessio and Richard about this on IRC today. Richard mentioned that the fix can be done and integrated into EAP.
I'll check whether there's JBPAPP issue already created for this. If not, I'll create one now.