If you would define a double spend as a TX in which the same input(s) are part of a transaction that would prevent a separate, previously propagated TX that someone though was going to be confirmed, then this is very much possible.
0-conf respend attempts happen every day. As was mentioned, the network actually tries to keep as nodes from seeing both. This site tracks the ones it sees though:
http://respends.thinlink.com