Specifically, the zeromq.node library uses 100% of the CPU spinning in a busy-wait loop. There are plans to switch to a more reasonable architecture, but the author hasn't had the time to actually do it yet.
Wait a few months and I'm sure all this discussion will be horribly obsolete, of course.