Node has no special ability to proxy and distribute work across multiple processes. Erlang, Hadoop, OpenMPI, those are things with special abilities to distribute work across processes. "Being able to use sockets" is not a "special ability", not even if you add the word "asynchronously". I'm not aware of a language environment of any significance now where you can't use "asynchronous" sockets. You are trying to build an ability, not harness something that already exists. There's nothing wrong with that, but it's a bit premature to put something like that right in the logo.
There are a few projects that specifically take advantage of node's ability to proxy and distribute work across multiple processes.
Check out these projects:
http://learnboost.github.com/cluster/
https://github.com/nodejitsu/node-http-proxy
https://github.com/substack/dnode
Or my very early prototype botnet thingie: https://github.com/isaacs/sodn