It is not "qualified" because the process using a heap is paused while the heap is collected. In a concurrent GC, nothing is paused.
that's a silly distinction, because if you are running multiple threads on a single CPU, or even multiple threads on multiple CPUs, in most situations, then you're simply pushing the 'pausing' down to the hardware/os which is doing the preemption.
Thread preemption has nothing to do with garbage collection pauses. An Erlang process that allocates a lot will spend more time being paused, irrespective of its priority which might otherwise let it run uninterrupted. I'm not going to continue this "argument" further.
That doesn't make it 'not a garbage collector' and it also doesn't make it 'not concurrent'.
> tuning may be required at the extremes
that is very rare, and if that is disqualifying for a concurrent GC, then Java is disqualified as a concurrent GC.