EJB over HTTP affinity only works with httpd-based load balancers

Currently, the EJB/HTTP client/server hard codes Tomcat-style session affinity logic:

• It creates a cookie named "JSESSIONID" which it uses to store the SessionID of the target SFSB.
• It appends the weak affinity of a given SFSB to the SessionID of the above cookie.

However, this logic only works with httpd-based load balancers.

To work with other load balancers (e.g. HAProxy), this logic needs to be more configurable.

Most load balancers that support cookie-based affinity, rely on a specific cookie (with a configurable name) that contains the name of the backend server for which a given request is intended.
In general, the EJB/HTTP client already stores the SessionID of the SFSB within a response header, so, unless the user is using an httpd-based load balancer, a separate JSESSIONID cookie is generally redundant.