The issue comes out when osgi framework boots (at jboss startup) and is not able to find com.wily.* classes.
The problem is solved with the following directive in the liferay portal properties file (portal-runtime.properties).
Normally the property is org.osgi.framework.bootdelegation. But in our case it has been customized with module.framework.properties.org.osgi.framework.bootdelegation
module.framework.properties.org.osgi.framework.bootdelegation=\
__redirected,\
com.liferay.aspectj,\
com.liferay.aspectj.*,\
com.liferay.portal.servlet.delegate,\
com.liferay.portal.servlet.delegate*,\
com.sun.ccpp,\
com.sun.ccpp.*,\
com.sun.crypto.*,\
com.sun.image.*,\
com.sun.jmx.*,\
com.sun.jna,\
com.sun.jndi.*,\
com.sun.mail.*,\
com.sun.management.*,\
com.sun.media.*,\
com.sun.msv.*,\
com.sun.org.*,\
com.sun.syndication,\
com.sun.tools.*,\
com.sun.xml.*,\
com.yourkit.*,\
sun.*,\
com.wily.*
Anyway now everything works.
Thanks
Luca Razzi