the paragraph https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/html-single/migration_guide/#migrate_jax_ws_2_2_requirements_for_webserviceref
is a little unclear on first reading, as there is referenced Java SE 7 javadoc for for javax.xml.ws.Service but talking about Java EE 7 or Java EE 6 which should have the JAX-WS 2.2 style contstructor ready.
What confused me more was that that API changed in Java SE 6 not in Java EE6 and due some code in JBossWS 4 it was
hidden behind the scene the not required migration, but now for EE 7 it is. So I would suggest to clarify it more to have something like:

"Containers must use JAX-WS 2.2 style constructors, using the WebServiceFeature class, to build clients that are injected into
web service references. In EAP 6 JBossWS 4 hide that requirement, but due upgrade to JBossWS 5 and underlined dependencies, the requirement is now a must. This means that user provided service classes injected by the container must implement JAX-WS 2.2 or
later by adding javax.xml.ws.Service constructor with WebServiceFeature parameter(s) into existing code - see
https://docs.oracle.com/javase/7/docs/api/javax/xml/ws/Service.html#Service(java.net.URL,%20javax.xml.namespace.QName,%20javax.xml.ws.WebServiceFeature...)
or
https://docs.oracle.com/javase/8/docs/api/javax/xml/ws/Service.html#Service-java.net.URL-javax.xml.namespace.QName-javax.xml.ws.WebServiceFeature...-

This issue is in both 7.0 and 7.1 Migration guide.