[eluser]WanWizard[/eluser]
I had that implemented at one point. But reverted everything, since it doesn't solve anything. You just postpone the problem, as after two ID rotations, the original ID would have disappeared.
How do you know it's not the ajax call? This issue is that an ajax call causes the ID rotation, without a proper cookie update client side. Every action you do after that, from a page reload to clicking a link, will send the now outdated cookie to the server, causing a 'loss of session'.