Jetty still running after SIGINT

[alesya-h]

I start application server with bundle exec rackup -s Jetty -p 3000
Here is fragment of ps axf
948 pts/1 Ss 0:00 | _ -bash
3335 pts/1 Sl+ 0:08 | _ /usr/bin/java -Djdk.home= -Djruby.home=/home/me/.rvm/rubies/jruby-1.6.6 -Djruby.script=jruby -Djruby.shell=/bin/sh -Djffi.boot.library.path=/home/me/.rvm/rubies/jruby-1.6.6/lib/native/ppc-Linux:/home/me/.rvm/rubies/jruby-1.6.6/lib/native/x86_64-Linux:/home/me/.rvm/rubies/jruby-1.6.6/lib/native/i386-Linux -Xmx500m -Xss2048k -Djruby.memory.max=500m -Djruby.stack.max=2048k -Dsun.java.command=org.jruby.Main -Djava.class.path= -Xbootclasspath/a:/home/me/.rvm/rubies/jruby-1.6.6/lib/jruby.jar org/jruby/Main /home/me/.rvm/gems/jruby-1.6.6/bin/bundle exec rackup -s Jetty -p 3000
3352 pts/1 Sl+ 0:13 | _ /usr/bin/java -Djdk.home= -Djruby.home=/home/me/.rvm/rubies/jruby-1.6.6 -Djruby.script=jruby -Djruby.shell=/bin/sh -Djffi.boot.library.path=/home/me/.rvm/rubies/jruby-1.6.6/lib/native/ppc-Linux:/home/me/.rvm/rubies/jruby-1.6.6/lib/native/x86_64-Linux:/home/me/.rvm/rubies/jruby-1.6.6/lib/native/i386-Linux -Xmx500m -Xss2048k -Djruby.memory.max=500m -Djruby.stack.max=2048k -Dsun.java.command=org.jruby.Main -Djava.class.path= -Xbootclasspath/a:/home/me/.rvm/rubies/jruby-1.6.6/lib/jruby.jar org/jruby/Main /home/me/.rvm/gems/jruby-1.6.6/bin/rackup -s Jetty -p 3000

After I hit Ctrl+C process 3335 got terminated but 3352 now has no parent and still running and working.
3352 pts/1 Sl 0:13 /usr/bin/java -Djdk.home= -Djruby.home=/home/me/.rvm/rubies/jruby-1.6.6 -Djruby.script=jruby -Djruby.shell=/bin/sh -Djffi.boot.library.path=/home/me/.rvm/rubies/jruby-1.6.6/lib/native/ppc-Linux:/home/me/.rvm/rubies/jruby-1.6.6/lib/native/x86_64-Linux:/home/me/.rvm/rubies/jruby-1.6.6/lib/native/i386-Linux -Xmx500m -Xss2048k -Djruby.memory.max=500m -Djruby.stack.max=2048k -Dsun.java.command=org.jruby.Main -Djava.class.path= -Xbootclasspath/a:/home/me/.rvm/rubies/jruby-1.6.6/lib/jruby.jar org/jruby/Main /home/me/.rvm/gems/jruby-1.6.6/bin/rackup -s Jetty -p 3000

Additionally rackup's --pid switch does not work - rack.pid file does not get created.