Communication between R3 client and R3 service will not have such a flaw. But we need to be backward-compatible with R2 client, too. The R2 protocol flaw I know of is that it creates a connection per request. R2 provides a workaround via connection pooling, which reuses a connection for more than one request and R3 will reuse a connection for more than one request by default. Please let me know if there's more protocol flaw I don't know. R3 is still open for a change. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166875#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...