The first thing you would ask is “since it won’t be running on Chrome/etc., In what JS host/engine will this JS app be running?”
Then, “How will the app handle multiple, concurrent user requests?”.
And, “How do I start a TCP listener in Ember/JS?”
I can imagine that all of those are possible, as it is just JS after all. But you won’t be using any of Ember to do so other than an app entry point. You’ll likely find a friendlier path using something designed for the back-end, though.