Please reread what I wrote; it is not. Let's do the second variant: to determine whether N is odd or even, compute:
e1 = E(N/N) (equals E(1)) ; 1, encrypted
b1 = E(N & 1) ; equals e1 iff N is odd
; (least significant bit of N)
e2 = E(1+1) ; 2, encrypted
b2 = E(N & 2) ; equals e2 iff second bit is set
e4 = E(2+2) ; 4, encrypted
e4 = E(N & 4) ; equals e4 iff third bit is set
e8 = E(4+4) ; 8, encrypted
Etc.
Each line is one homomorphic operation. You need ceil(2 log(N)) lines to recover N.So you're thinking of a private key cryptosystem, where the ciphertext and the plaintext have the same length and E(.) is bijective, but in the case of ElGamal and public-key encryption in general, E(.) is not actually a function in the mathematical sense and instead encrypts one-to-many. (In fact if memory serves, n plaintext bits become 2n ciphertext bits in ElGamal.)
If that's the case in general then you could indeed compute E(1) := e_div(E(N), E(N)) and e_and(E(N), E(1)), but you could not say that E(N & 1) === E(1) if N is odd, because even though N & 1 = 1 and we've got a nice property of mathematical functions which says that if a = b then f(a) = f(b), this isn't a mathematical function and the one-to-many nature foils precisely this sort of naive comparison.
That requires that encrypting X always produces the same bits. Reading on ElGamal on Wikipedia learnt me that it does not guarantee that; it also doubles messages in size, as you thought. That will thwart this attack for any reasonable size of the encoded messages.
One could do the comparison inside the crypto system, but that would not help either, as one cannot check the outcome of such a comparison.
Besides, the big foreseen uses of HE is in applications where the confidential data is going to be changing constantly, so once you've finally figured out what one value was, it'll be worthless to have it because computation has continued.