Use of (automatic) reference counting is not new (see, for obvious example, Python), and is certainly being used as a form of garbage collection.
There are many forms/strategies of garbage collection, reference counting is one of them. Trying to argue that we're never going to have "garbage collection" on iOS is utterly bizarre -- it's being added in iOS 5! It's just taking a different form.
This requirement that the application programmer participate in memory management contributes more to the distinction than the fact that the Cocoa reference counting scheme imposes less runtime overhead than most robust garbage collectors of the sort used by Java or Python.
The new Automatic Reference Counting used by Cocoa is still different from traditional garbage collectors, because it is implemented without imposing any more runtime overhead than the manual scheme. ARC is essentially a preprocessor phase that infers (based on coding conventions) where to place the calls to -retain and -release. None of the complex logic for tracking the lifetime of an object is done at runtime. It's done at compile time, if at all. (ARC differs from full-fledged robust garbage collectors like what Java has in that ARC can't handle situations like cycles in the object graph. Handling those cycles is one of the main things that makes writing a high-performance Java-like GC non-trivial, but ARC simply chooses to not be that automatic.)
Did I just step into the twilight zone?
All those terms sometimes get used differently in different contexts sometimes, but I think that's what's usually meant by them.
Some interesting references:
http://en.wikipedia.org/wiki/Garbage_collection_(computer_sc...
http://www.research.ibm.com/people/d/dfb/papers/Bacon01Concu...
http://www.google.com/search?q=garbage%20collection%20refere...