We've also seen this problem, and Sam Berlin, one of our open source programmers, identified a bug in the code that is causing it. It's fixed on our main code branch, and the fix will go out with the next major LimeWire release.

Thanks.