why sourceid idff 2.0 only supports jboss?

Sourceid recently released idff(1.2) java toolkit version 2.0. In fact, 
we have used its beta version earlier. Although we have some trouble 
running the demo(for example, the artifact cannot run smoothly), we are 
more concern about its WEB CONTAINER support.
We've seen someone post such question in this list, but without any answer.
To us, earlier version sourceid idff toolkit that supports tomcat can be 
better used, because once support tomcat, there is a wide spectrum of 
environment that it can work on, including jboss. While only supports 
jboss (we will describe why we are sure of this in next paragraph), the 
valid environment becomes A POINT: ONLY JBOSS, not anything else. We 
cannot understand this change: is it because commercial consideration, 
or is it because jboss' implementation is easier?
Why we think new version ONLY supports jboss? While compiling, if 
untouched, everything goes well. But if we elimilate jboss classpath in 
the ant build.xml file, there will be errors. The package requiring 
jboss is "Implementation", which Castlepeak relies on.

To our understanding, it is not nessasary to implement idff 1.2 under 
jboss. And to our knowlage, there exist "lasso" that do idff1.2 in C++, 
it could be invoked from .NET, Java, Python, PHP, etc.
We don't think it is a good choice to only target one environment while 
implementing standards. For anybody insterested in this would like to 
make it  run on more servers.