Unexpected behaviour of the persistence if EJB's are invoked remote inside of a server application in EAP6

Issue

• If a Java EE application use a second EJB application which is depoyed on other server instances, which might be clustered, multiple invocations are routed to different servers.
  Sometimes the invocations are successful, but there are situations where one of the invocations in that sequence is not able to read data which was written before or even read stale data.
  This behaviour is different to former EAP versions where the same application worked correct.
• Is it possible to have a Sticky policy for Node selection for EJB client to invoke stateless session beans?
• EAP 4 provide a TransactionStickyLoadBalancer policy to be able to use container managed persistence, is there a similar policy in EAP 6?