I agree with you on this as it might hide app issues. This happened when I (accidentally) ran my app with node 0.6.20. Running on 0.8.18 I never encountered errors regarding this. I left it like this for compatibility and classified it as a node issue