EJB3 load balancing doesn't keep client's node list up to date when jndi call-by-value is used

An issue with EJB3 load-balancing not updating a client's node list after a cluster node disconnects has been resolved in this release or EAP 5. It was found that using the call-by-value attribute, with isolation as a property was causing FamilyClusterInfo to be overwritten by a JNDI call that triggers demarshaling of the MVP. A 'finally' block has been added to the code to ensure the FamilyClusterInfo object is not overwritten once updated with new topology.