Have you tried disabling the non-webMethods packages (you can do this by modifying the manifest.v3 file under each package physical directory) and starting?
At minimum, disable the non Wm* packages. At max, disable everything but make sure you leave Default, WmPublic, and WmRoot enabled.
Once the server starts (if it does) you can selectively enable packages through the Administrator and see which one chokes.
This is an easy test to identify if a particular package or circular dependency in packages is causing a problem.
#webMethods#Integration-Server-and-ESB#webMethods-Archive