1) It was developed in-house at Google
2) It reflected the hi-DPI of the screen.
Evidently they decided to turn "Pixel" into a brand, and I suppose they figured that the in-house tablet they developed warranted the title (if you look at the thing, its aluminum design does resemble the panel half of a Chromebook Pixel).
So I suppose they now use the Pixel brand to either represent that style or to indicate that it's in-house hardware.
The latter. [1]
"Pixel is Google designed hardware; Nexus is hardware we work closely with partners to design"
[1] https://www.reddit.com/r/IAmA/comments/3w3x7p/hi_im_andrew_h...
Meaning that it may be in part aimed at dogfooding the Android platform internally, much like how Microsoft employees run beta version of their software to root out early bugs and such.
Also offering the device for sale may provide some means of covering the expense of having them made, as usually factories demand certain minimum amount ordered before they start a production run.
I think it's most likely due to Apple's weak enterprise management tools for OS X [1] and the mid-2009 cyber attack on Google (Operation Aurora [2]) which was the result of one or more Internet Explorer zero-day vulnerabilities.
[1] http://www.theregister.co.uk/2013/11/27/google_mac_support/
In other words, Google doesn't have much of a strategy other than throw a bunch of stuff against a wall and see what sticks.
http://www.google.com/search?q=problems+with+my+surface+book
It's called Pixel instead of Nexus, (it's running Android), so it's confusing to many people, on the market positioning side...
At the same time, on the technical side, Android team, after telling us to use Fragments to have nice tablets+phone experience for a few years, seems to not care about fragments anymore. Notably appcompat and design libraries don't work correctly in Fragments anymore... And the Google apps show this very clearly.
If Google apps are not supporting tablets correctly, why should we?