I've had this happen to me before, and usually it was because there was something more fundamental going wrong with the Puppet Server that was causing connection issues, and the SSLv3 thing is just a red herring.
In our case, we ended up having CPU contention issues which was causing really bad Puppet Server performance. One thing to try is to stop the puppet service on all your managed nodes, and restart the puppet server. Check if you can compile a catalog on a single node, or if you still get the issue. If you no longer have the problem, it might be a performance issue with your Puppet Server.