[eluser]CroNiX[/eluser]
I wonder if this can be fixed by using a "queue" for session writes, where it would store all requests to write to the session and perform only one db write/issue one cookie when the session class __destructs for everything stored in the queue.
I do something similar for logging cron jobs performed. While processing the cron jobs it is storing everything that is performed in a class property (array) and when the cron job finishes and hits the __destruct(), it sends an email listing everything that was processed. Maybe something similar could work here as well.