So, the details of the upcoming changes to Internet Explorer are here: http://msdn.microsoft.com/ieupdate/
Since I doubt any appeal against the ruling by Microsoft will be completed by "early next year" we can assume that there will be incarnations of IE out there that have this, ahem, functionality; even if they win an appeal and revert the behaviour back to previous there will be some people with the modified version. So, you're going to have to handle it.
Once more it has to be made clear that I just do not understand the US Patent system - quite how popping up a dialog gets round the patent I really don't understand but there we go. The "work-around" of dynamically writing the object tags I do understand (it takes the interpreted content out of the source document stream and makes it programmed content) and is neat. It is also worth noting that it is explicitly clear that ActiveX controls that do not reference external data are unaffected by the patent (quite right IMHO).
Very interesting is that applications hosting the Web Browser ActiveX control or MSHTML directly also do not, by default, get this behaviour. So - all those myriad (hundreds of them) custom browsers out there will not suddenly start behaving with the unpatented method, they will continue to behave as IE which is, according to Eolas, patented. Presumably this means MS are saying, "go on then Eolas, sue the lot of them for license fees" with the expectation that a) a lot of 'em are free products and therefore not worth suing or b) cheap low volume products and therefore not worth sueing or c) worth sueing, but as soon as you do the vendor (you wait for it, wait for it) flips a bit in the program et, viola, you can't sue me. Very cute.
As far as the MeadCo products go, Zeepe 7 should be completely unaffected so long as you stick to the zeepe: namespace elements (object tags introducing behaviours are, again rightly, unaffected and Zeepe is a custom host - the Zeepe 7 zeepe:browser element will change to default to Internet Explorer behaviour). ScriptX is unaffected because it does not use the <param> tag and internal usage does not reference external data.
What is affected is licensed ScriptX usage using the Security Manager control. Usage of this control, despite the fact that it has no UI will have to change because it references the external license file.