How Troublesome Is "Scalars Leaked" Warning?

All:

I'm getting a "scalars leaked" warning from an independent thread after
it finishes and detaches from another thread in my program.   I was
curious if this was an artifact of ithreads in Perl v5.8 and also if I
should be concerned in a production environment.

Here is the high level sequence of events:

- thread 0 (main) spawns thread 1 (a TCP accept() connections loop)
- a connection gets opened in thread 1, messages exchanged (with client)
and the connection is closed
- just after closing the connection (and before looking for the next)
thread 2 is spawned which does some further processing and communication
(involves pre-existing sockets).  no sockets are opened or closed in
this thread
- thread 2 completes, detaches and the error message results (no other
messages)

Please note that I have several other threads in the program that
perform without generating error messages.

My current hypothesis (if I may be so bold) is that socket connections
are treated as independent processes and that thread 2 is complaining
about the state of thread 1 after it detaches.

Does this look familiar to anyone?

Thanks and best as always,

Steve