On Websphere I believe this to be a problem with the websphere JAX-WS engine instantiating the Web service endpoints instead of getting them from the Spring container. You can see this by adding a breakpoint in the constructor, or even better in one of the setters for any spring wired bean in your Web Service IMPL class. You can see that Spring will initialize the beans and yet they will be null when accessed after a web service call. This leads me to believe that they are not the same bean.
So in effect the bean properties are getting wired but the instance of the impl being used by WebSphere (or I would assume Glassfish) is not.
One solution would be to make the impl ApplicationContextAware and use a static ApplicationContext. Then you can access any bean in the context using the GetBean methods made available via the static context.