That sounds like everything's working the way it should. Until the "first" request is authenticated successfully and the response comes back to the browser/device, your app doesn't have session credentials. Sending multiple simultaneous unauthenticated requests will thus all need to authenticate individually -- and making matters worse, may create multiple sessions on the server, so as they come back your session info (as represented by your JSESSION ids) will rapidly run through all the new sessions until settling on the last one.
I would suggest changing your application flow to let your first request go by itself first and not submit any other requests until that (authenticated) response is received.
Flex SDK engineer
Appreciate the response, and I think that answers my question that this is not some sort of known issue or bug, but I do need to clarify my problem. The first request to the server is an automated login and the session is set correctly. Only after this are the mutliple requests made at the same time. I think it's about 7 requests that all fire at the same time about every 10 seconds (polling system). Sometimes this will function correctly for multiple rounds of requests and everything works fine for 30 seconds or so. Sometimes the first round of requests after the login will fail (session does not persist). Sometimes the first round will succeed and only half of the second round will succeed before failure. I lose the session pretty randomly but I don't think the application has ever made it past 3 or maybe 4 rounds of requests.
Based on your description it's not clear if the problem is the server or the client losing sessions. I'd suggest doing some session tracking, either through tracing out the session IDs or trapping them with a web proxy in the middle, and see where in this barrage of requests is the session information being lost, and who (client or server) is the first one to stop using it.
-- Tom Kraikit
Flex SDK engineer