BatchletRunner currently spawns a wather thread to check if the current job has been requested to stop. This wather thread terminates when the job is requested to stop, or when the job execution terminates. So it may still be alive after the batchlet terminates, which takes up thread resources.