Apache hasn't changed that such since 2.0 when it comes to basic connection handling. When it comes to handling tons and tons of connection, its I/O architecture is the problem, irregardless of prefork or worker.
That said, the comparison is pretty yawning. It's been known for years that Apache with its non-evented architecture is not good at handling massive amounts of connections; there's really no point at comparing with Apache anymore. I'm more interested in how this stacks up against Lighttpd or Nginx.
They're essentially comparing apples to oranges:
Apache's worker MPM uses system threads, whereas Erlang uses its own internal scheduler, so that at the system level, there is only one process.