Hi Ian.Paul
Thanks for acknowledging, but I spent some time and figured it out. I would just document it here in case anyone runs into this. The problem was actually with layout.jade from Express framework, the default behavior is to include all contents of index.jade into the body of rendered page, so nowjs was being included twice while it showed up only once in the head tag and once in the body(which I never bothered to check). Though Firefox ignored this, Chrome went ahead and established more than one connections thus nowjs.on("connect") was being called twice.
But an interesting discovery here is that a new clientId is assigned to the same user, lets say if I were to open a new tab for my app, will this behavior persist or is it possible to identify this client as already connected?
Sorry for the false alarm, btw.