I have been provided a HotFix for testing that is a potential fix/improvement for this problem. I will be testing it on my side.

Here's the email from Barry at Microsoft:
----------
I have been testing a hot fix that was recently released that had a similar desctiption to this issue. My results are mixed. It takes longer to fail and when it does the error message is not the same. I don’t know if I am actually hitting on something good or my environment needs rebuilding due to all the changes and tests I have done. I am going to forward it to you and ask if you have time to test it on your end and see if there are any positive results with it.
----------

Here's the KB http://support.microsoft.com/kb/2028965


If anyone else wants to test this hotfix I can email it to you (if there isn't a way to download it online).