Spring Beans as Services

We have started to use the spring bean support to upload new services, which works fairly well, however we are seeing that the WSAS pulls every public method as a wsdl action. Is there a specific annotation that we can use to tell the WSAS to ignore certain methods? We are also currently exploring updating the spring jar to 2.5 and using spring annotations to set the dependencies as opposed to the "getter/setter" pattern required in spring 1.

Additionally, we see that every service call to the spring service instantiates a new bean tree to handle the request. Theoretically, what would call for the opposite, where the wsas obeys the spring definition attributes for prototype and singleton bean instantiation? I think it works this way probably because of how the WSAS threads handle individual requests independently, aka a concurrency problem?