Safari/ExpressJS etag interactions are broken in some subtle way. This manifests itself in Safari continuing to display its cached copy of the logged-in '/' (i.e. dashboard) even after visiting /logout.
This seems to be the same issue as mentioned here: http://stackoverflow.com/questions/18811286/nodejs-express-cache-and-304-status-code