The tnsping always checks up the listener for making sure that it could establish the connections. On this case, it some or other finds the connection information, i.e it was looking at your old configurations. This is what I could think on on this regard and know that Windows has all kinds of mistry things in it. As a last resolt, check your sqlnet.ora too.
BTW, check making a connection to the database through the sqlplus and see whether it would go through, it should infact complain you now of not finding the tnsname entry. To see that the listener does not have an entry, check
If it lists your deleted service as one of its entry, then you can think about bouncing your server. If it doesn't then you can ignore every thing.
TNSPING doesn't have anything to do with the actual database connecting. It doesn't tell you if the database is up or down or even present. It doesn't try to connect to the database, after all how would it connect as you can't provide any username/PWD when calling it!
What TNSPING does is it only tries to reach (ping) the listener. So it only checks if the listener on the specified machine is up and if it listens to the specified port.
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?