Process explosion

 Hi guys,
 I came home today to a mailbox full of cron jobs failing because the
"couldn't fork". Sure enough, netbsd has a conservative process limit
(160), and I'm running pretty close to it - primarily because of the
130(!) emu processes.
 I only have a single emu instance running, and within that I'm
serving some instances of ircfs. ps within emu gives 45 processes
which look believable - I don't think there's anything funny going on
on that side of the fence.
 So, my questions are:
1) is this behaviour expected?
2) is there a way to limit the process growth?
 I've upped my limit for the moment, I'll see if the number of procs
keeps growing or not...
-sqweek