Yes I have. They told me to try this forum.
Here is an extract of what they answered:
Hello Name1
I think it's caused by the application pool recycle, as we said originally the ASP Session ID is destroyed and a new one created when the application recycles ... the problem is that application does not then delete the old ID because it has no prior knowledge of it .. I doubt they factored in for the fact that some users such of yourself would have visitors with browsers open for such long periods of time, when they designed it.
We have increased the application recycle time of application pool your site utilises, this will help as you should only now have 6 ASPSESSIONID's being created per 24 hours.