I run 3 instances with arbiter:

REPEAT N IN (0-2)
mongod.exe --dbpath "C:\Databases\Replica\Repl

{N}" --logpath "C:\Databases\Replica\Repl{N}

\Logs\Log.txt" --port 4000

{N}

--replSet RPL

Arbiter:
mongod.exe --dbpath "C:\Databases\Replica\ReplArb" --smallfiles --nojournal --noprealloc --logpath "C:\Databases\Replica\ReplArb\Logs\Log.txt" --port 40003 --replSet RPL

initiate, add, addArb.

40000 - master,
40001 - secondary,
40002 - secondary
40003 - arbiter

1) Kill - 40000
2) 40001 became primary
3) Kill 40001
ooops...

40002 - secondary
40003 - arbiter

And 40002 still waiting to be PRIMARY.
What wrong ?

P.S When i run 2-member replica set with arbiter - it's work ok and election were held, but this configuration is fail.