Thanks Tom for your comments.
I have in fact determined that this affects all machines, PC, Macs, Linux, etc, that sit behind this firewall. Further, I've determined that the firewall does block the iWebSite.js file specifically, and that if you turn off filtering for this specific exploit, the firewall allows the page through.
I'm now trying to determine what signature the firewall is looking for. Based on Microsoft's TechNet bulletin on the topic, it should be scanning the response body of any HTTP request for the following strings "urn:schemas-microsoft-com:vml", "<v:", "v\:", "xmlns:v=", and finally "url(#default#vml)", non of which show up in the iWebSite.js file. It's possible I suppose that ZyXEL is looking for some other string to identity potential malicious sites, and possibly erroneously so. I'll have to wait until I hear from the. If you're not familiar with this kinda of technology, this firewall is doing so called Deep Packet Inspection (DPI), where the firewall is inspecting the content of each package for possibly malicious code--as any ordinary js or css file could possible contain such malicious code.
As this is obviously a case of an accidental match, I was hoping maybe someone had seen this before, as a little reformatting of the offending file, which I know now is iWebSite.js, would let the file pass the filter.