Importing Sikuli is causing a Jenkins Failure!

Hi,
A strange behavior that I'm facing when running my sikuli tests from jenkins...
The test cases themselves are passing, but at the end of the job jenkins is loosing the connection with the client:

Process leaked file descriptors. See (http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build
for more information)
FATAL: Remote call on AU_9 failed
java.io.IOException: Remote call on AU_9 failed
at hudson.remoting.Channel.call(Channel.java:789)
at hudson.Launcher$RemoteLauncher.kill(Launcher.java:953)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:540)
at hudson.model.Run.execute(Run.java:1738)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)

I followed the link in the error and there they are explaining about this problem and how it can be avoided (by starting jenkins with processTree disabled or by creating a deamon\service that is runing all the time and preventing from killing the child job).

However, my concern is why that is happening only when I do import for the sikuli in my test suite (even without running the TCs)?

Regards.

Start by reproducing the import-only Sikuli test suite in Jenkins and compare it with a run that does not import Sikuli. Use the reported leaked-file-descriptor message and Jenkins remote-call stack trace to identify what remains open; done means explaining the import-specific cause and documenting a verified resolution.