I guess you won't get these problems when you are running stunnel in pipe or pipe-client mode. It is supposed to run in multi-threaded mode only when it is listening on a port.
This seems to be a very good explanation to me as I run stunnel for pop3s via inetd.
Thanks, Arthur.
