Alrighty, for service implementations:
If you're deploying an EJB (standalone jar file in the deploy folder) - include your wsdl and all supporting metadata files in the JAR file's WEB-INF/wsdl folder of the jar.
if you're deploying a service within a WAR file - include your wsdl and all supporting metadata files in the WAR file's WEB-INF/wsdl folder of the jar.
Modify the implementation class's @WebService annotation
@WebService(serviceName = "MyService", name = "MyService", targetNamespace = "MyNamespace", wsdlLocation = "WEB-INF/wsdl/MyWsdl.wsdl")
Note: If you're using servlet container style authentication (http basic, digest, etc), such as with a WAR, clients will have to authenticate if they do not already possess the wsdl/xsds locally.
To work around this, add a directory to your WAR that does not require authentication and copy your wsdl's there. Then tell your clients to use that wsdl. Revise the endpoints in the unprotected dir to have the correct endpoints listed.
Bonus point: include this with your automated build process (a la jenkins)