I would be surprised if Spring BlazeDS's use of class-based AOP proxies is causing the problem, because we only advise one class (flex.messaging.endpoints.AbstractEndpoint) which in a typical scenario never has more than a handful of instances (however many you've configured in services-config.xml) created at application startup time. What led you to this conclusion? Have you perhaps also turned on class-based AOP proxies globally for the application?
Jeremy Grelle
Staff Engineer, Web Products Team
SpringSource