More news from MS Tech Support. This is regards Adobe's side of the problem:
"Great news from Adobe!
"They have worked on the issue and they recognized it is a bug in the reader! They have logged the bug and they will work on releasing a fix in the next Adobe reader release. They have no ETA as to when the next release will be."
So this doesn't address being able to run 2008 r2 as a web server at all. Someday Adobe will issue a release, and someday the majority of the population will have it installed.
With regard to Microsoft's side of the issue:
"I am still pushing however for a server solution even with this news, I don’t have an ETA as to when our product team will decide if they are going to take a fix for that or not, but I’ll keep you posted."
It doesn't matter if it's red paint or one 5-gallon bucket of paint; if Microsoft doesn't do any change, anybody serving PDFs from a web site or web app will need to write code to handle the PDF requests or else not upgrade their web server to Windows Server 2008 r2. In the short term, Adobe's fix probably isn't going to be enough of a solution. Personally, I'd prefer the OS code to remain "pristine" and RFC-compliant, but in the real world, I've got a web site that needs to serve PDFs to a public that's not always so good about updating their plugins.
Okay...to be honest....I've already written the code to handle the PDFs and am about to move it to production. I'll leave it to others to debate who is being RFC compliant and who is not and does it matter.....