If the library exists in osgi/state, some module brings it. You
might look at osgi/state for informational purpose,
but you should not think on modifying anything on that
level. It's just a cache that the OSGi runtime has under control.
Rather identify who brings it and fix that module.
How? The lpkg files in osgi/marketplace are actually zip format, so
you can open them with standard unzip and inspect them. Or locate the
dependency in Liferay's source, where you likely can grep it.
