So, even though the driver has no packages, if an ECMA object which IS part of a package and is linked to the driver via the ECMASript tab of the driver, it can't be removed from said driver after applying the changes because the ECMA is package managed....

https://bugzilla.netiq.com/show_bug.cgi?id=1036164

Hacking the DirXML-Policies on the driver and importing the change is the only way to resolve the linkage.