It almost certainly is, and if someone finds something faster and reports it, a pull request will be made in Julia to make that faster way be the way X!=Y is computed.
If you check (eg with @edit) you will find that it ultimately dispatches to (==)(A::AbstractArray, B::AbstractArray) which is written efficiently (in the sense that it will return early if it finds a discrepancy).
Generally, if you are concerned about efficiency, it is best to just learn about the relevant tools — the performance tips is a good starting point for efficiency of compiled code, while for algorithmic efficiency you should just learn to understand Julia code.