I was wondering if there were any reason why trying to introduce pooling of stateless-scoped instances would be non-trivial. (I don't believe we are doing this today; instead we create a new instance each time.)
Otherwise I was planning to give it a try, after noticing specifically that the reference proxy injection is slow. I realize there are considerations, when, say, a stateless component has a reference with a conversational-interface, since the spec says that ref injection begins a conversation. However if you're using stateless components, you should clearly know that the container may or may not give you a new instance, so if you choose to inject a ref. to a conversational intf then you leave it up to the container to start a new conversation when it creates a new stateless instance. So I don't see this as a problem. Would be interesting to hear other concerns before prototyping. Thanks, Scott
