I don't think this is Chrome-specific, but rather how HTTP cookies are specified.
In particular:
Similarly, cookies for a given host are shared
across all the ports on that host, even though the usual "same-origin
policy" used by web browsers isolates content retrieved via different
ports.