mhearse:

I have no Apache-fu, but perhaps it manages its child threads and kills 'em when it considers them unresponsive?

The only other suggestion I can think of is to perhaps suspend all other processes that aren't absolutely critical for your application and see if the signals go away. Then you can use a binary search to figure out which one of the ones you turned off was the culprit.

...roboticus