I've seen this happen to daemons when a badly configured client is hammering them with connections that drop immediately. After enough of these, the server gets a connection, but then it gets an ENOTCONN error when it tried to get a peer address. I assume it's something to do with operation system tables filling up with half-open connections.

This was on a Linux box.

c.