To reproduce:
1. Start Fitnesse on a target machine
2. Setup a Jenkins job to build using the 'Fitnesse instance is already running' option
3. Set the 'HTTP Timeout (ms)' to a value which will cause the test to timeout

Result:
> Jenkins build is classed as Aborted when the timeout value is exceeded, however the Fitnesse tests on the target machine continue to run

Expected Result:
> Jenkins build failing or aborting should force Fitnesse for stop tests