Alessio I can confirm that is related to the jira issue https://issues.jboss.org/browse/JBWS-2235
We followed the workaround described in jira issue to resolve the problem
However, because we were using a top down approach with more than one namenspace, we found another workaround using the wsdlLocation annotation and not let jboss generating the wsdl (ok it's not properly a workaround, it's a different approach in building ws)
I will try to have information when jboss ws4 will be merged in EAP (I think future EAP 6.x)
Thanks a lot for your support.
Ciao,
Giovanni