Thanks for pointing out this forum post Visvanath. Looks like someone else was suspicious of that moodledata/muc/config.php file. I find it interesting that this occurred with my newly built environment that uses memcache and never had issue with any of my other test instances. I guess we need to include deleting moodledata/muc folder during any upgrade or site migration in moodle docs.
I am still trying to get the time to test this situation again with consistent results but I cant really do it in my current dev environment without risking my production instance. I cant really use the excuse "I am applying the scientific method!" if I knock out production again by reproducing the error. This error has yet to occur when i copy a out of the box moodle instance with memcache and a muc/config.php. It only has happened to my production instance. I had the idea of building a completely isolated LAMP cluster that has no ability to communicate with anything outside the cluster and an isolated client machine but that takes time and resources I do not have atm.