No sooner did I post this that I saw one of our developers had added their own verison of jquery to the main clientlib our page component overlay uses. Commenting out the inclusion of this jquery library resolved the issue. I'm going to guess there was a conflict between the jquery that ships with AEMaaCS and this one.